Workstation uptime, maintenance, and reboot service

ABSTRACT

Managing updates to executable programming code on a computer system in a computer network. A maintenance service utility is configured to launch a maintenance procedure at a specified time during operation of the computer system. Operation of a maintenance timer utility is activated during startup of the computer system to track and monitor the amount of time the computer system has been operating since startup. The maintenance service utility determines if there any updates to the executable programming code that require installation. The maintenance procedure is launched after a specified time if there are updates to the executable programming code. The computer system is automatically rebooted to install the updates to the executable programming code. A maintenance service editor utility enables the maintenance service utility to be configured to launch the maintenance procedure after a specified time if there are updates to the executable programming code.

BACKGROUND OF THE INVENTION

The present invention relates generally to management of clientworkstations in a large wide area computer network and, moreparticularly, to monitoring of client workstations to keep workstationscurrent with operating system and antivirus software updates.

A large enterprise will typically have a wide area network (WAN) withmany thousands of workstations that are connected to various servers inthe network. Managing operating system updates to combat computerviruses in this environment is very problematic since large numbers ofthese workstations are desktop computers that are left running when theemployees that use them leave work. The employees simply log back in thefollowing work day and the desktop does not get rebooted on a regularbasis. Regularly restarting a computer activates program updates andsoftware patches that protect personal computers and the network formviruses. Problems with computer memory and applications locking up alsocan be attributable to failure to reboot a computer on a regular basis.

The traditional approach to the problem has been to educate employees toreboot their workstations on a daily basis, but this approach has hadlimited success in many large enterprises.

Thus, there is a need for an automated approach to workstation updateand maintenance to solve the maintenance and virus proliferationproblems on an enterprise wide area network caused by a lack of regularworkstation reboots, and that does not require the cooperation ofindividual computer users. There is significant business value in theavoidance of Information Technology (IT) support center phone calls anddesktop support staff visits caused by failure to have the operatingsystem updates and other software patches installed on a timely basis.

SUMMARY OF THE INVENTION

The present invention is directed to an automated method for managingcomputer system updates and maintenance in an enterprise computer widearea network. The automated solution provides basic rebootfunctionality, the ability to configure and manage workstations on alarge network, the ability to centrally manage exceptions, and theability to warn users before the actual computer reboot occurs.

The invention is implemented in several software tools that worktogether to monitor individual workstations on the wide area network andreboot the workstations when needed for proper maintenance. Aworkstation uptime utility measures the amount of time that aworkstation has been running without reboot. A workstation maintenanceutility triggers the workstation reboot if the time without rebootexceeds a pre-set threshold.

The purpose of the workstation maintenance utility is to provide aservice which will launch maintenance procedures at desired intervals ona workstation or server. In an exemplary embodiment, the workstationmaintenance utility has five different possible methods for launching amaintenance procedure: (1) after one hour of workstation startup andevery hour after; (2) after every specified wait period; (3) on aparticular day of the week and hour; (4) on a particular date and hour;and (5) on a daily basis during a specified hour.

In one aspect of the invention, a method is provided for managingupdates to executable programming code on a computer system in acomputer network. A maintenance service utility is configured to launcha maintenance procedure at a specified time during operation of thecomputer system. A maintenance timer is activated during start up of thecomputer system to track the amount of time that the computer system hasbeen operating since start up, without rebooting. The maintenanceservice utility determines if there are any updates to the executableprogramming code that require installation. If there are updates to theexecutable programming code, the maintenance service utility launchesthe maintenance procedure after a specified time. The computer system isautomatically rebooted to install the updates to the executableprogramming code.

In another aspect of the invention, a system is provided for managingupdates to executable programming code on a computer system in acomputer network. The system includes a maintenance uptime componentthat is activated during startup of the computer system to track theamount of time that the computer system has been operating sincestartup. The system also includes a maintenance service component,cooperative with the maintenance uptime component, for determining ifthere are any updates to the executable programming code that requireinstallation and launching a predefined maintenance procedure at aspecified time during operation of the computer system. The maintenanceservice component automatically reboots the computer system to installupdates to the executable programming code. The system further includesa maintenance service editor component for configuring the maintenanceservice component to launch the predefined maintenance procedure after aspecified time if there are updates to the executable code.

In yet another aspect of the invention, a computer program product isprovided for managing updates to executable programming code on acomputer system in a computer network. The computer program productincludes a computer readable medium having computer readable codeembedded therein. The computer readable medium includes: programinstructions that configure a maintenance service utility to launch amaintenance procedure at a specified time during operation of thecomputer system; program instructions that activate operation of amaintenance timer utility during startup of the computer system to trackan amount of time that the computer system has been operating sincestartup; program instructions that determine if there are any updates tothe executable programming code that require installation; programinstructions that launch the maintenance procedure after a specifiedtime if there are updates to the executable programming code; andprogram instructions that automatically reboot the computer system toinstall the updates to the executable programming code.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other advantages and aspects of the present invention willbecome apparent and more readily appreciated from the following detaileddescription of the invention taken in conjunction with the accompanyingdrawings, as follows.

FIG. 1 illustrates processing logic for the workstation maintenanceutility in accordance with an exemplary embodiment of the invention.

FIGS. 2A-2E illustrate various exemplary screen displays generated bythe workstation uptime utility.

FIG. 3 illustrates an exemplary Service Control Manager view with theworkstation maintenance utility service selected.

FIG. 4 illustrates an exemplary workstation maintenance utility serviceproperties display.

FIG. 5 illustrates an exemplary workstation platform registry editor.

FIG. 6 illustrates an exemplary workstation maintenance utility serviceeditor display for local mode operation.

FIG. 7 illustrates an exemplary popup menu for editing a workstationmaintenance utility application.

FIG. 8 illustrates an exemplary add/modify form for a workstationmaintenance utility application.

FIG. 9 illustrates an exemplary display for editing a workstationmaintenance utility application.

FIG. 10 illustrates an exemplary workstation maintenance utility serviceeditor display for remote workstation access.

FIG. 11 illustrates an exemplary workstation maintenance utility serviceeditor display for debug mode operation.

FIGS. 12 A-12B illustrate an exemplary workstation maintenance utilityservice editor display for poll time operation.

DETAILED DESCRIPTION OF THE INVENTION

The following description of the invention is provided as an enablingteaching of the invention and its best, currently known embodiment.Those skilled in the art will recognize that many changes can be made tothe embodiments described while still obtaining the beneficial resultsof the present invention. It will also be apparent that some of thedesired benefits of the present invention can be obtained by selectingsome of the features of the present invention without utilizing otherfeatures. Accordingly, those who work in the art will recognize thatmany modifications and adaptations of the invention are possible and mayeven be desirable in certain circumstances and are part of the presentinvention. Thus, the following description is provided as illustrativeof the principles of the invention and not in limitation thereof sincethe scope of the present invention is defined by the claims.

The invention is implemented in several software tools that worktogether to monitor individual workstations on a wide area network andreboot the workstations when needed for proper maintenance. Aworkstation uptime utility measures the amount of time that aworkstation has been running without reboot. A workstation maintenanceutility triggers the workstation reboot if the time without rebootexceeds a pre-set threshold. The workstation maintenance utility has theability to be configured to launch a maintenance application at aspecified time after the startup of the workstation. In the context ofthe invention, workstation is defined to encompass desktop computer,laptop computer, server computer, client computer, handheld devices andany other computing devices that are connected to, or have access to,the wide area network.

Workstation Maintenance Utility

The workstation maintenance utility is a service that enablesconfiguration of a large number of workstations to run specificprocesses at a scheduled time without every workstation running specificprocesses at the same time. The workstation maintenance utility can bemanaged remotely. The time that a workstation is set to run is relativeto the startup time of the service or workstation. Since everyworkstation will have a different startup time, the time the processesare scheduled to run will be at random intervals preventing thepotential problem of network overload.

The workstation maintenance utility is installed using a standardinstallation program such as Microsoft Windows Installer forworkstations operating on the Microsoft Windows platform. The commandline for workstation maintenance utility can also install and uninstallthe service. Once installed as a service, the workstation maintenanceutility will check every hour to see if it has anything assigned for itto do. If the workstation maintenance utility has nothing that is readyto be run, it simply goes back to sleep for another hour.

The workstation maintenance utility is command line executable. In anexemplary embodiment in a Windows platform environment, typingWinMaint-? at the command line will display the following message:

SYNTAX:

WinMaint [−i] [−u] [−?]

−i—Install WinMaint as a service.

−u—Uninstall WinMaint as a service.

−?—This help screen.

The workstation maintenance utility component of the invention can beconfigured to operate in several ways. In an exemplary embodiment, whenthe service or workstation is started, the workstation maintenanceutility sleeps for one hour before it wakes up and checks if it has anytasks to perform.

There are several possible methods that the workstation maintenanceutility can use to determine if a process is ready to be launched. Thesemethods include, but are not limited to, the following:

-   -   1. launch the service after the first hour since boot up, and        every hour thereafter at the same minute;    -   2. launch the service after a specified amount of wait time,        specified in milliseconds;    -   3. launch the service on every occasion of a specified day of        the week and at a local time zone hour;    -   4. launch only on a specified date and at a local time zone        hour;    -   5. launch every day during a specified local time zone hour.

The workstation maintenance utility deals in increments of hours in anexemplary embodiment. The minute of launch is determined by the time(i.e., minute) that the workstation or service started up, therebyproviding random launch capabilities. When the workstation boots up andthe workstation maintenance utility is started, it will sleep for onehour before it checks to see if there is any code to launch. Afterwards,it will check once every hour to see if the conditions are right tolaunch the given code.

FIG. 1 illustrates the high level processing logic for the workstationmaintenance utility component in the exemplary embodiment. Processingbegins as indicated in logic block 100 with the workstation start up.The workstation maintenance utility process goes to “sleep” for one hourand then wakes up as indicated in logic block 102. In decision block104, the workstation maintenance utility determines if there is anythingto do. If there is no process to run, the workstation maintenanceutility returns to logic block 102 and goes back to sleep for anotherhour. If it determines there is a process to run, a determination ismade as to whether or not to run the process immediately as indicated inlogic block 106. The workstation maintenance utility can go back tosleep for an additional period of time (logic block 108) or run theprocess immediately (logic block 110). When the process completes asindicated in logic block 112, the workstation maintenance utilityreturns to logic block 102 to wait for the next cycle to begin. Itshould be noted that once the workstation starts up, the workstationmaintenance utility runs continuously.

To launch a particular maintenance procedure the following steps arerequired: (1) place the executable code in a directory accessible by theworkstation; (2) under the registry key, “HKLM\SOFTWARE\EnergyCompany\WebIcons\Maint\”, create a sub-key with a unique name for thecode to be launched; and (3) under the new sub-key, create the set ofvalues from the table below which will cause the code to launch at thespecified time.

TABLE SleepMethod: 0 = Launch after the first hour of bootup and everyhour afterwards at the same minute. 1 = Launch after every specifiedamount of wait time, specified in milliseconds. 2 = Launch on everyoccasion of a specified day of the week and local time zone hour. 3 =Launch only on a specified date and local time zone hour. 4 = Launchevery day during a specified local time zone hour. Exec: String Valuewith the name of the executable code including the path, e.g.,c:\EnergyCo\Webicons\UpTime.exe. Param: String Value can either be blankor contain the parameters to pass to the executable code. Iterative: 0 =Code will not run if it is still in memory. 1 = Code will run again evenif it is still in memory.

If the Sleep Method value is zero, no other values are required. If theSleep Method value is one, the user must specify the amount of time inmilliseconds to wait before launching the code. The specified time doesnot begin until one hour after bootup or service start.

When the Sleep Method value is one, the workstation maintenance utilitywill launch a thread after the first hour which will then go to sleepfor the specified amount of time. After the specified amount of time haspassed, the thread will then launch the code specified by “Path” and“Exec”. When the thread is launched, a flag value in the createdapplication key is set to one to keep the thread from being launchedagain. After the code is launched, the flag is set to zero. If thecomputer is rebooted before the specified sleep time has ended, the flagvalue is automatically reset to zero and the thread will be launchedagain after an hour has passed.

If the Sleep Method value is two, the user must enter a numeric valuerepresenting the day of the week, and a numeric value representing thehour of the day that the code should be launched. The code will belaunched every time this day is reached at the hour specified. The codewill not launch if an hour is not specified. The range of values for dayof the week are zero (Sunday) though six (Saturday). The hour of the dayis a numeric value representing the hour to launch the code. The rangeof values is 0-23. The hour refers to the local time zone.

If the Sleep Method value is three, then the user must enter a month,day, year and hour of the day for the code to be launched. The month isexpressed as a numeric value representing the month in which the codeshould be launched. The range of values is 1-12. The day is a numericvalue representing a date that exists within that month. The range ofday values is 1-31, but if 31 does not exist in the given month, thecode will not be launched. The year is a numeric value representing theyear that the code should be launched. The year value will be a fourdigit number such as 2001. The hour is a numeric value representing thehour to launch the code. The range of values is 1-24. The hour refers tothe local time zone.

If the Sleep Method value is four, the user must enter a numeric valuerepresenting the hour to launch the code. The range of values is 1-24.The hour refers to the local time zone.

When Sleep Method 2, 3 or 4 is used, the workstation maintenance utilitywill begin checking after the first hour and continue checking everyhour for the correct time specified. The code will usually not launchexactly at the specified hour, but instead within an hour after thespecified time has passed. This is based upon what time the workstationwas brought up and the service was started. In other words, if thecomputer is brought up at 8:04 AM and the Sleep Method is 2 for Sundayat 10:00 PM (or 22 as specified in the ‘Hour’ value), the code will morethan likely launch on Sunday at 10:04 PM.

If the registry value for “Debug” is set to one under“HKLM\SOFTWARE\Energy Company\WinMaint\”, this setting will cause theworkstation maintenance utility service to detail an activity log fileunder c:\energyco\logs called WinMaint.log. It is best to use the debugfeature only for a short period during troubleshooting since the logfile will otherwise continue to grow. It is also a good idea to deletethe file when troubleshooting has been completed so that the next timeit is needed it starts fresh. To change the debug value, it is necessaryto stop and start the service. After setting the debug value fortroubleshooting purposes, the debug feature may be turned off by settingthe value to zero and stopping and starting the service. All otherregistry settings can be made without stopping and starting the service.The service will simply re-check the settings each hour.

Workstation Uptime Utility

The workstation uptime utility is installed using a standardinstallation program such as Microsoft Windows Installer forworkstations operating on the Microsoft Windows platform. While it hasthe ability to run in a stand-alone mode, it is best operated as part ofthe workstation maintenance utility. The workstation uptime utility is acommand-line driven utility which pops up Windows-based messagesaccording to how long the computer has been operating since the lastreboot. With proper configuration, the workstation uptime utility willprompt a user to reboot their workstation on a regular basis. Then ifthe user fails to reboot the workstation after a certain period of time,the workstation uptime utility will automatically reboot theworkstation. It will do so with plenty of warning to the user, evengiving a configurable countdown to the user before it performs thereboot.

The workstation uptime utility also includes a built-in exceptioncapability. This allows certain workstations operating sensitiveprograms to be exempted from automatic reboot by being in a globalworkstation network group. Exempted workstations will not receive anyprompts from the workstation maintenance utility for reboot, but centrallogs will still be maintained as to individual workstation uptime. Thecommand line format for the workstation uptime utility in aWindows-operating environment is as follows:

usage: winuptime [−?]|[−e]|[−l]|[−p #]|[−f # #[#][#]]|[−o # #[#][#]]

where:

no parameter simply displays the uptime;

-   -   −? displays this message;    -   −e displays exception information;    -   −l outputs to a log file on \\logs.energyco.com\logs$\UpTime and        c:\EnergyCo\Logs;    -   −p if # days or more, displays a popup giving the user an        opportunity to reboot;    -   −f first # prompts as above after specified days; after second #        forces reboot; if 0 or # days or more, displays a popup giving        the user an opportunity to reboot immediately; otherwise the        workstation will reboot automatically in one hour; the 3rd # is        for an optional offset for running under a service; the 4th # is        for an optional # seconds which the force will wait for the        reboot; the default time, if this is not used, is 60 minutes;    -   −o works exactly like the −f except that it overrides the        exception process.

FIGS. 2A-2E illustrate various exemplary screen displays generated bythe workstation uptime utility. FIG. 2A provides an example of a messagereceived from running the workstation uptime utility with no parameters.FIG. 2B illustrates an example message received when running theworkstation uptime utility with the “−?” parameter. It basicallyprovides a help screen for the workstation uptime utility. FIG. 2Cillustrates an example message received when running the workstationuptime utility with the “−e” exception parameter. If the workstation isin the global exception group, it will not go through a forced reboot.FIG. 2D illustrates an example message received when running theworkstation uptime utility with the “−f” parameter using the prompt andforce parameters. FIG. 2E illustrates an example message received whenrunning the workstation uptime utility with the “−p” parameter and thenumber of days to prompt.

The following is a list of the different log types:

#_MachineName_UpTime.log

nr_MachineName_UpTime.log

r_MachineName_UpTime.log

f_MachineName_UpTime.log

ex_MachineName_UpTime.log

fex_MachineName_UpTime.log

The log file created by the workstation uptime utility will varyaccording to the type of argument passed. The log file arguments are asfollows:

-   -   −l log file will be named #_MachineName_UpTime.log, where # is        the number of days the workstation has been up;    -   −p if the user responds with “yes” the log file will be named        r_MachineName_UpTime.log; if the user responds with “no” the log        file will be named nr_MachineName_UpTime.log;    -   −f for the prompt period, the log names will be the same as for        the −p argument; for the force, the log file will be named        f_MachineName_UpTime.log unless the workstation is in the        exception global group; if the workstation is in the exception        global group, the log file will be named        ex_MachineName_Uptime.log for the prompt period; although the        user will not receive a prompt, the log will still be created;        -   for workstations in the exception group, during the force            period, a log file will be created named            fex_MachineName_UpTime; although the user will not be            prompted and the workstation will not be rebooted, the log            will still be created; every log created will have the            amount of time the workstation has been up, the workstation            name and the user name; every log will also state whether            the user elected to reboot when prompted.

The logic for logging will vary according to the argument as follows:

-   -   −l the logging concept is that the workstation uptime executable        can be run on many workstations to collect uptime statistics;        the central log server collects a log from each workstation on        which the workstation uptime utility is run; the folder where        the files accumulate can then be sorted by the number of days of        uptime and then the        -   workstation name; such a collection will show at a glance            which workstations are problems;    -   −p the collection of log files can be sorted to show all        workstations for which the user has either declined reboot or        accepted reboot; there will be many cases in which the        workstation will be in both groups with different dates;    -   −f the prompt period will work exactly like the −p; the force        will be sorted together by workstation name; the exception        workstations will also be sorted together.        Workstation Maintenance Service Editor

FIG. 3 illustrates an exemplary Service Control Manager view with theworkstation maintenance utility service selected. FIG. 4 illustrates anexemplary workstation maintenance utility service properties editordisplay. This figure shows the service name, description, path toexecutable, startup type, and service status. FIG. 5 illustrates anexemplary workstation platform registry editor. The workstationmaintenance utility is configured using the registry editor. This figureshows one application (“Uptime Force”) configured to be run by theworkstation maintenance utility. Other applications would simply followthe “Uptime Force” under the “WinMaint” key.

FIG. 6 illustrates an exemplary workstation maintenance utility serviceeditor display for local mode operation. The workstation maintenanceutility service editor is a graphical user interface (GUI) tool whichwas written for the purpose of managing the workstation maintenanceutility on many workstations remotely. It is a simple executable writtenin Visual Basic 6.0 which can be run from any workstation on the networkand connect to any other workstation on the network.

When the workstation maintenance utility service editor(“WinMaintEditor”) first comes up, it is in local mode, meaning that itwill look at the local workstation to see if the workstation maintenanceutility (WinMaint) is installed. If the workstation maintenance utilityis installed, it will report on the status of the service and whatapplications are installed as part of the service, plus theirconfiguration. In the example above, the workstation uptime utility(“WinUpTime”) is configured as “UpTime Force” on the local workstation,as shown in the “Defined Applications” window of the form. Under“Application Settings” is shown how the “UpTime Force” application isconfigured to be launched by the workstation maintenance utility.

In the upper left hand corner of the service editor display is a trafficlight icon which is used to turn on and off the ability to stop andstart the workstation maintenance utility. Clicking the traffic lightwill cause it to turn green. The lower left hand part of the serviceeditor display has a status bar which gives the status of the service.In the example illustrated in FIG. 6, the service is running. Byclicking the icon next to the traffic light (with the circle in thecenter), the user can stop the service as long as the traffic light isgreen. Clicking the icon with the arrow in the center will cause theservice to start again. Then clicking the traffic light will cause it toturn red, locking the service control feature.

To modify an application in the workstation maintenance utility, theuser simply clicks the name of the application to be changed and thenright clicks on the application name. This will cause a small popup menuto appear, as illustrated in FIG. 7, enabling the user to add, modify,or delete the application. Selecting “Add” on the popup menu will givethe user the opportunity to add an application to the functionality ofthe workstation maintenance utility. Selecting “Modify” or “Delete” willdirectly affect the application selected. Selecting “Delete” will removethe application from the workstation maintenance utility service.Selecting “Add” or “Modify” will bring up windows that allow the user toconfigure an application. Selecting “Add” will be for a new application;selecting “Modify” will bring up the current configuration of theselected application so that changes can be made.

FIG. 8 illustrates an exemplary add/modify form for a workstationmaintenance utility application. This display helps to make sense ofwhat otherwise could be construed as cryptic parameters required forsetting up the workstation maintenance utility. The “Application Name”,“Executable Path” and “Application Parameters” fields areself-explanatory. “Application Name” is the name which is shown in the“Defined Applications” window and in the logs from WinMaint. “ExecutablePath” is the complete path to the executable file which the workstationmaintenance utility is to launch. The “Application Parameters” settingsprovide the arguments that the workstation maintenance utility shouldpass to the application when it is launched. The “Sleep Method” is usedto specify when a maintenance procedure should launch after aworkstation is started.

FIG. 9 illustrates an exemplary display for editing a workstationmaintenance utility application. With the use of the drop down menu for“Sleep Method”, it is readily apparent that the exemplary embodiment hasfive different possibilities. Each selection will alter the form toreflect the configuration methods. As shown in FIG. 9, the form showsthe setup for “Specified Wait” method of sleep and the status bar at thebottom of the form gives more information about how the “Sleep Method”is used.

Using “Specified Wait”, the form offers a time calculator on the righthand side. “Specified Wait” is measured in milliseconds. By specifyingthe hours, minutes and seconds of wait time, the calculator determinesthe specified amount of time in milliseconds. In the example shown inFIG. 9, the system checks the workstation every six hours, orequivalently, 21,600,000 ms. The workstation maintenance utility editorallows the user to enter an amount of time in hours, minutes, secondsand milliseconds which will automatically be calculated intomilliseconds with the number placed in the “Wt” or wait field at thetop. Every number that the user inputs adds the appropriate number ofmilliseconds to the “Wt” field at the top. After the user finishesconfiguration, the user can select “Set Application.” This causes theuser-defined configuration to be written to the registry for theworkstation maintenance utility to pick up at its next cycle.

The “Hourly” sleep method is the simplest to configure. The service willrun the application every hour that it wakes up to discover if it hasanything to do. Day of the week selection for sleep method is madesimple by providing the drop down boxes of days and hours which can beconfigured. Date and time selection for sleep method provides a dropdown for the months, the day, the year (up to five years in the future),and the time. Launching daily at a specified time is also configuredusing the drop down selection for the time of day.

The “Iterative” checkbox is generally not used. However, its functioncan be appropriate under certain circumstances. With the “Iterative” boxchecked, the workstation maintenance utility will launch anotheriteration of the application even if one thread is already waiting forits time to come up. In other words, with the application set to launchafter a specified wait of six hours, after the first hour that theservice starts it will launch a thread which will go to sleep for sixhours before it wakes up and runs. With “Iterative” checked, this samethread will be set every hour. This means that at the end of the firstsix hour wait, the application will run every hour.

FIG. 10 illustrates an exemplary workstation maintenance utility serviceeditor display for remote workstation access. On the right hand side ofthe form are two radio buttons which are used to toggle between “Local”mode and “Remote” mode. When the workstation maintenance utility editorcomes up, it defaults to “Local” mode. To switch to “Remote” mode, theuser simply selects the “Remote” radio button, then types in thecomputer name in the “Machine Name” field on the left hand side of thedisplay and clicks the “Get” button. This will contact the remoteworkstation and display its configuration information the same as itdoes for local mode. Functionality is the same in remote mode, includingthe ability to stop and start the service.

FIG. 11 illustrates an exemplary workstation maintenance utility serviceeditor display for debug mode operation. In debug mode, the workstationmaintenance utility will write a continuous debug log during itsoperation. Since this log can fill up quickly, it is usually not usedunless there is a problem and troubleshooting methods are needed. Theuser can turn this feature on by going to the “View” menu at the top ofthe form and selecting “Debug Mode”. This allows the “Debug Mode”checkbox to show up on the form. The user can then check “Debug Mode” toturn it on or uncheck it to turn it off. Likewise to remove the “DebugMode” checkbox from the form, the user can simply reselect “Debug Mode”from the “View” menu causing it to disappear from the form.

By default, the workstation maintenance utility is set to wake up everyhour to check and see if it has anything to do. This option can actuallybe adjusted to be any other time using the poll time feature. FIGS. 12A-12B illustrate exemplary workstation maintenance utility serviceeditor displays for poll time operation. To use this feature, the usergoes to the “View” menu shown in FIG. 12A and selects “PollTime”. Thiswill cause the “PollTime” calculator form shown in FIG. 12B to pop up.It should be noted that this calculator is very similar to the“Specified Wait” time calculator used to set up the sleep mode for theapplication. Since poll time needs to be configured in milliseconds,this calculator allows the user to enter a time, e.g., 1 hour, and theamount of time in milliseconds is automatically displayed in the “PT”field at the top.

The present invention can be utilized for monitoring system uptime onlarge number of networked workstations for reasons other than rebootingfor virus protection and regular maintenance. The invention can be usedto trigger maintenance type jobs on a managed schedule. The inventioncan also be used to manage automatic rebooting on a large number ofworkstations for other reasons.

The system and method of the present invention have been described ascomputer-implemented processes. It is important to note, however, thatthose skilled in the art will appreciate that the mechanisms of thepresent invention are capable of being distributed as a program productin a variety of forms, and that the present invention applies regardlessof the particular type of signal bearing media utilized to carry out thedistribution. Examples of signal bearing media include, withoutlimitation, recordable-type media such as diskettes or CD ROMs, andtransmission type media such as analog or digital communications links.

The corresponding structures, materials, acts, and equivalents of allmeans plus function elements in any claims below are intended to includeany structure, material, or acts for performing the function incombination with other claim elements as specifically claimed.

Those skilled in the art will appreciate that many modifications to theexemplary embodiment are possible without departing from the spirit andscope of the present invention. In addition, it is possible to use someof the features of the present invention without the corresponding useof the other features. Accordingly, the foregoing description of theexemplary embodiment is provided for the purpose of illustrating theprinciples of the present invention and not in limitation thereof sincethe scope of the present invention is defined solely by the appendedclaims.

What is claimed:
 1. A method for updating a computer system, the methodcomprising: identifying an update to an executable programming code thatrequires installation on the computer system; configuring themaintenance service utility to launch a maintenance service procedureafter a predefined period of time; configuring the maintenance serviceutility to operate in an iterative mode to periodically launch anotheriteration of the maintenance service procedure based on an expiration ofthe predefined period of time and at a specified time period that isshorter than the predefined period of time; launching, via a thread, themaintenance service procedure after the predefined period of time bylaunching an update executable code comprising the update; andlaunching, via the thread, the another iteration of the maintenanceservice procedure to update the executable programming code.
 2. Themethod of claim 1, wherein the configuring the maintenance serviceutility to launch the maintenance service procedure comprises: selectingsleep mode for the maintenance service utility.
 3. The method of claim2, wherein the sleep mode comprises at least one of: an hourly sleepperiod, a user specified sleep period, a user specified day of the week,a user specified date and time, and a daily sleep period.
 4. The methodof claim 1, further comprising: selecting a wait time for themaintenance service utility to remain dormant.
 5. The method of claim 1,further comprising: rebooting the computer system when a maintenancetimer utility identifies that an amount of time that the computer systemhas been operating since startup exceeds a predetermined thresholdlimit.
 6. The method of claim 5, further comprising: activating themaintenance timer utility during startup of the computer system.
 7. Themethod of claim 1, wherein the launching the maintenance procedurefurther comprises: creating a set of values including a sleep modevalue, a unique executable code name, and a path to the executable codeto launch.
 8. The method of claim 7, wherein the created set of valuesfurther comprises: at least one parameter to pass to the executable codeto launch.
 9. A non-transitory computer readable medium storingcomputer-readable code that when executed by at least one processorcauses the at least one processor to perform: identifying an update toan executable programming code that requires installation on thecomputer system; configuring the maintenance service utility to launch amaintenance service procedure after a predefined period of time;configuring the maintenance service utility to operate in an iterativemode to periodically launch another iteration of the maintenance serviceprocedure based on an expiration of the predefined period of time and ata specified time period that is shorter than the predefined period oftime; launching, via a thread, the maintenance service procedure afterthe predefined period of time by launching an updated executableprogramming code comprising the update; and launching, via the thread,the another iteration of the maintenance service procedure to update theexecutable programming code.
 10. The non-transitory computer readablemedium of claim 9, wherein the computer-readable code is furtherconfigured to cause the at least one processor to perform: selecting asleep mode for the maintenance service utility.
 11. The non-transitorycomputer readable medium of claim 10, wherein the sleep mode comprisesat least one of: an hourly sleep period, a user specified sleep period,a user specified day of the week, a user specified date and time, and adaily sleep period.
 12. The non-transitory computer readable medium ofclaim 9, wherein the computer-readable code is further configured tocause the at least one processor to perform: selecting of a wait timefor the maintenance service utility to remain dormant.
 13. Thenon-transitory computer readable medium of claim 9, wherein thecomputer-readable code is further configured to cause the at least oneprocessor to perform: rebooting the computer system when a maintenancetimer utility identifies that an amount of time that the computer systemhas been operating since startup exceeds a predetermined thresholdlimit.
 14. The non-transitory computer readable medium of claim 13,wherein the computer-readable code is further configured to cause the atleast one processor to perform: activating the maintenance timer utilityoccurs during startup of the computer system.
 15. The non-transitorycomputer readable medium of claim 9, wherein the launching themaintenance procedure further comprises: creating a set of valuesincluding a sleep mode value, a unique executable code name, and a pathto the executable code to launch.
 16. The non-transitory computerreadable medium of claim 15, wherein the created set of values furthercomprises: at least one parameter to pass to the executable code tolaunch.